-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vm: Add a transaction execution function #3186
Conversation
7c53d2c
to
15623e0
Compare
eaf0a6a
to
87fd7a8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, very nice how we can get rid of the execute in test utils
It might be good to wait for a second opinion from @miloszm or @herr-seppia though
87fd7a8
to
f957ca8
Compare
f957ca8
to
8ebe6ed
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Tested a binary based off of commit 8ebe6edc4c98a3cf654cba457034a02597e8cb19 against testnet. Works as expected and is backward compatible.
The base branch was changed.
8ebe6ed
to
e59474d
Compare
9b98d54
to
e59474d
Compare
In order to move
execute
to ourvm
some contract-deployment functionalities had to move as well:dusk_core::transfer::Transaction.deploy_charge
dusk_core::transfer::data::Bytecode.verify_hash
dusk_core::abi::gen_contract_id
Resolves #3185